Toll-free telecommunications management platform

ABSTRACT

Methods and systems are provided for the management, routing and reporting of toll-free telecommunications calls and data. Methods and systems are provided for pre-populating a call routing template based on natural language inputs and populating telecommunications routing codes at nodes of a call routing decision tree to generate a call routing template that may be identified and presented to a user interface based at least in part on a natural language input.

RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.15/373,387, filed Dec. 8, 2016, which is a continuation of U.S.application Ser. No. 14/928,575, filed Oct. 30, 2015, now U.S. Pat. No.9,549,066, issued Jan. 17, 2017, which claims priority to U.S.Application Ser. No. 62/073,976, filed Nov. 1, 2014.

The above applications are hereby incorporated by reference in theirentirety.

FIELD OF INVENTION

This disclosure is related to the operation, control and management oftoll-free telecommunication lines.

BACKGROUND

Businesses increasingly use toll-free telephone numbers for providingcustomers with a convenient and cost-free means of communicating withthem and their various departments, such as customer service andtechnical support representatives. With the proliferation of toll-freenumbers and advanced business analytics for receiving, routing, andlogging, the use of such numbers has come increased complexity inmanaging toll-free numbers.

SUMMARY

Provided herein are methods and systems for pre-populating a callrouting template based on natural language inputs comprising,associating a natural language element with a telecommunications routingcode, the telecommunications routing code associated with decision treelogic associating routing of incoming calls to a toll-freetelecommunications number; storing the association; receiving a naturallanguage input from a user, the natural language input includes thenatural language element; selecting the telecommunications routing codebased at least in part on the stored association; populating thetelecommunications routing code at a node of a call routing decisiontree to generate a populated call routing decision tree; and storing thepopulated call routing decision tree as a call routing template that maybe identified and presented to a user interface based at least in parton the natural language input.

In embodiments, a natural language input may be a text or voice element.A text element may be a scanned text element. A voice element may beobtained by voice recognition software.

In embodiments, decision tree logic may determine the call path taken byan incoming toll-free call to a termination number, the call path takenby an incoming toll-free call based at least in part on the time of daythe incoming call is received, the call path taken by an incomingtoll-free call based at least in part on the geographic location of thedevice from which the incoming call is received, the call path taken byan incoming toll-free call within a business entities telecommunicationssystem, or some other call path outcome.

Further provided herein are methods and systems for creating a callrouting decision tree, the system comprising a user device of a userconfigured to receive a natural language input from a user; select astored call routing template, wherein the selection is based at least inpart on a stored association of the call routing template and a naturallanguage element that is included in the natural language input; presentthe stored call routing template to the user within a graphic userinterface; receive a command from the user, through the graphic userinterface, to associate the selected call routing template with atoll-free telecommunications number indicated by the user; and store theassociation between the call routing template and the toll-freetelecommunications number.

In embodiments, the command from the user may be text-based, such as atext-based item that is presented within the graphic user interface in amenu or other location. In embodiments, the command may be a voicecommand.

Further provided herein are methods and systems of a user device forpresenting data to a user in real time regarding changes in metadataassociated with a toll-free telecommunications number, the user devicecomprising a user device of a user configured to receive an indicationof a change in status of a toll-free communications number, wherein thetelecommunications number is associated with a responsible organizationthat processes toll-free telecommunications; update a metadatumassociated with the toll-free communications number based at least inpart on the change in status; store the metadatum; receive a statusrequest from a user relating to the responsible organization; andpresent the user with a graphic representation of the telecommunicationsnumber's status. In embodiments, the presentation may include presentinga status for a plurality of telecommunication numbers associated withthe responsible organization, wherein the status presented is based onreal time status changes occurring over a toll-free telecommunicationsnetwork.

Further provided herein are methods and systems of toll-freetelecommunications data visualization comprising presenting a datavisualization dashboard to a mobile application on a client device,wherein the presentation includes a selectable listing of toll-freetelecommunications data parameters; receiving a selection from theclient device of the toll-free telecommunications data parameters toanalyze and at least one type of data analysis to perform; retrieving,in substantially real time, data relating to the selected toll-freetelecommunications data parameters; analyzing the data according to theat least one type of data analysis; and presenting to the mobileapplication a summary of an analytic result.

In embodiments, the status may indicate availability of the toll-freetelecommunications number for purchase, that the toll-freetelecommunications number has been reserved, historical usageinformation relating to the toll-free telecommunications number, abilling action required for the toll-free telecommunications number, anupcoming availability of the toll-free telecommunications number, orsome other status information associated with the toll-freetelecommunications number.

BRIEF DESCRIPTION OF THE FIGURES

Various features will become apparent to those skilled in the art fromthe following detailed description of the disclosed non-limitingembodiments. The drawings that accompany the detailed description can bebriefly described as follows:

FIG. 1 depicts a simplified illustration of the toll-free managementplatform.

FIG. 2 is a schematic illustration of a basic decision tree structure.

FIG. 3 illustrates a simplified customer record routing, created usingthe toll-free management platform.

FIG. 4 depicts a simplified flow diagram for constructing a call routingtemplate based at least part on natural language inputs from a user.

Skilled artisans will appreciate that elements in the figures areillustrated for simplicity and clarity and have not necessarily beendrawn to scale. For example, the dimensions of some of the elements inthe figures may be exaggerated relative to other elements to help toimprove understanding of embodiments of the methods and systemsdisclosed herein.

DETAILED DESCRIPTION

The present disclosure will now be described in detail by describingvarious illustrative, non-limiting embodiments thereof with reference tothe accompanying drawings and exhibits. The disclosure may, however, beembodied in many different forms and should not be construed as beinglimited to the illustrative embodiments set forth herein. Rather, theembodiments are provided so that this disclosure will be thorough andwill fully convey the concept of the disclosure to those skilled in theart. The claims should be consulted to ascertain the true scope of thedisclosure.

The present disclosure includes a toll-free management platform (TFMP)for providing services to toll free subscribers and providers, enablingthem to manage a plurality of toll-free numbers and tasks associatedwith such numbers. Functionalities of the TFMP include, but are notlimited to, Number Administration (NA) and Customer Record (CR)administration.

FIG. 1 depicts the main functional components of the TFMP 100,illustrating examples of the functionality provided by the TFMP andinterfaces 104 to the TFMP. The NA functionality 108 may allow toll-freeproviders to search a pool of toll-free numbers using specified criteriaand reserve numbers that will be used by toll-free subscribers, andperform CR administration 118. This functionality may include, but isnot limited to, storing toll-free provider and telecommunications data110, reporting processes 112, billing, [and service control point (SCP),and management functionality 120 for the coordination with SCPs 122.Responsible organizations, also referred to herein as “RespOrgs,” 102,may utilize the TFMP 100. Reporting from the TFMP 100 may be back toRespOrgs or to other systems and platforms 124 that are external to theTFMP 100. The TFMP enables searching for any random number or to searchfor a plurality of numbers that are consecutive and/or include anindicated combination of digits. Since certain toll-free number codes(e.g. 800) and combinations of digits (e.g. repeating digits, digitswhose corresponding telephone keypad letter values spell a word orphrase) may be considered most desirable, the NA function 108 includescapabilities for searches and reservations to be handled so that atoll-free provider does not gain an advantage to reserve a giventoll-free number. The TFMP also enables tracking the overall assignmentof numbers for each toll-free provider in order to enforce regulationsfor toll-free number allocation specified by the tariff. NA may maintaina status for each number that reflects whether it has been reserved andwhether a customer record has been created and sent to SCPs. It ispossible to query the TFMP 100 for status and reservation informationassociated with a number.

The TFMP enables customer record administration, allowing toll-freeproviders to create a customer record and to specify when theinformation should be sent to SCPs. A reserved toll-free number maybecome active when routing information for the number, specified in acustomer record, is uploaded into SCPs. Customer records may be updatedor deleted and the send time updated prior to sending. Once a customerrecord has been sent, a new record may be created to update or deletethe routing specified by the previous record. The routing informationspecified in a customer record may include, but is not limited to:

-   -   An Area of Service (AOS) that specifies from where the toll-free        number can receive calls    -   The carrier that will route calls to the toll-free number    -   The terminating number that will receive calls to the toll-free        number    -   A set of rules that specifies different routing based on        criteria like time of day and area from where the call        originated

Carriers who have arrangements to carry calls for a toll-free providermay wish to approve customer records when routing for a toll-free numberhas been assigned to the carrier. The customer record function maymaintain a list of carriers and preferences for whether approval isrequired when a toll-free provider indicates the carrier in a customerrecord. A notification may be sent to a carrier when approval of acustomer record is required. In embodiments, each customer record mayhave an associated status. Customer records may be queried to view thestatus and information contained in the record, based on the permissionsof the user.

In another disclosed non-limiting embodiment, the TFMP may include auser interface functionality that allows manual access for human usersand mechanized access for systems (such as an application programminginterface) to make use of the NA and CR functions provided by the TFMP.Such systems may be embodied in a distributed computing environment,such as a “cloud” based computing network. In another embodiment, suchsystems may be hybrid networks, including usage of a cellular telephonenetwork (and associated mobile communication devices, such as smartphones), a distributed, cloud network and an enterprise networkassociated with a carrier or other business organization (and anycombination or sub-combination of such networks). The mechanizedinterface provided by the TFMP may allow external users to establishdata dynamic connectivity with the platform and gain access to itsavailable functions. The TFMP may maintain logins, passwords,encryption, authentication, and the like to provide security to limitsystem access to only authorized users. Permission levels that restrictaccess to TFMP's functions and to proprietary data may be assigned foreach authorized user, and stored locally or remotely to an enterpriseutilizing the TFMP, including within a computing storage facility thatis remote to, but operatively coupled, with the TFMP. In embodiments,the user interface functionality may provide real time notifications andother information to external users using mechanisms such as email andFile Transfer Protocol (FTP).

In another disclosed non-limiting embodiment, the TFMP may provide aninterface to send routing information from CRs to SCPs. The SCPManagement Function of the TFMP may enable management of interactionswith SCPs, including maintaining data connectivity, sending CRinformation at the specified date and time, and monitoring responses inorder to update customer record status. The SCP interface may include aninterface that is based on the specification provided by TM-STS-00798,CMSDB/SMS Interface Specification Manual and Interface Message Manual.

In another disclosed non-limiting embodiment, the SCP administrationfunctions of the TFMP may allow users to establish and modifySCP-related reference data in the system and send messages to the SCPnode and the Call Management Services Data Base (CMSDB) within the SCPto manage data tables at the SCP. Network management functions fortoll-free database services may involve the management of variousautomatic capabilities intended to monitor and control toll-free querytraffic and calling volumes at the SCPs, Service Switching Points,terminating switches, terminating subscriber lines, and the like. Whenvarious call volume thresholds are exceeded, the SCPs may triggerAutomatic Code Gapping (ACG) controls at the originating SSPs. TheTFMP's management functions may allow network managers to configure andadjust relevant control parameters. Data collection at the SCPs may berequested through the TFMP to provide network managers with surveillanceinformation that is useful to monitor traffic and analyze problems, suchas the detection of SCP overloads and excessive calling or excessiveineffective attempts to dialed codes.

In another disclosed non-limiting embodiment, the TFMP may enablereporting functionalities that allow tracking user actions, systemevents, performance statistics, and other events and formatting theinformation into reports for toll-free providers and systemadministrators. The TFMP may provide capabilities for users to requestreports and for delivery of report results in a plurality of formats.Reports may be requested online by users as per the assigned permissionsand delivered over the interface on which the report was requested.Requests may be made from any computing facility, including, but notlimited to, a personal computer, laptop computer, tablet, mobilecommunication facility (such as a smart phone), or some other type ofcomputing device. It may also be possible for users to request reportsoff-line using the TFMP. For example, a system administrator usinginformation provided by the platform may dynamically compile off-linereports. In embodiments, the TFMP may track and report on real timeevents that will result in charges to toll-free providers. The tariffspecifies the rate elements that may result in charges on a monthly billand the rate to be charged. These may include, but are not limited by,establishment of a system logon ID, monthly access to the system,reservation of a toll-free number, report requests, or some other typeof element. Information provided by the TFMP may be needed to calculatemonthly charges and create monthly bills that are sent to each toll-freeprovider.

The current practice of managing toll-free numbers and activities, andthe tools currently available to users for building a complex customerrecord, are very often single threaded and cumbersome. In addition, thecurrent industry practices do not provide the ability to define adefault customer record for a user, in part because it may not beintuitive to build a complex customer record. According to the methodsand systems presently disclosed, the TFMP may provide tools that workintelligently with the user, allowing a natural language input, such asEnglish words, to translate and map such language to signifiers that maybe less familiar to a user, such as call routing codes. This translationand mapping of natural language to toll-free number managementinformation and data may produce a dynamic, complex customer record,including using existing user records and usage data, to populateinformation for the user. This may speed the creation of complex routingand other metadata that is associated with a toll-free line, based atleast in part on the TFMP enabling the dynamic querying of the real timestatus of data that is associated with a toll-free number, guide theuser in providing the necessary natural language information that allowsthe TFMP to map such language to toll-free number metadata (e.g.,routing codes), and store and implement a complex decision treedescribing the actions to take for a given toll-free number.

In an example, the TFMP may provide a user interface in which a usertypes a command such as “Route all incoming calls made to toll-freenumbers having the extension 571 to the technical support staff.” TheTFMP may take this natural language input and map it to routing codes orother data corresponding to the natural language. In another example,the natural language may be selected from a menu that is provided in theuser interface of the TFMP, provided via voice command using voicerecognition software, via scanned text that is input to the TFMP, orusing some other means of conveying natural language. The CustomerRecord Template Builder (CRTB) of the TFMP may allow building a complexcustomer record template using a user interface, enabling that record tobe designated as the default customer record. Using the TFMP, atoll-free provider may build multiple complex customer record templatesfor their use and define a record as the default customer record,allowing the user to select the default with a single click, thusreducing their work effort.

In another disclosed non-limiting embodiment, the CRTB may lead a userthrough an initial customer data population (known as the CustomerAdministrative Data (CAD) portion), and also the call routing logic(Call Processing Record; known as the CPR portion) that is associatedwith a toll-free number, by utilizing the TFMP user interface toconstruct a decision tree logic structure with defined data nodesderived from the user's natural language inputs.

Based upon the decisions at the nodes in the decision tree that isconstructed by the TFMP, the user interface may drive down a branch to anew decision node ultimately driving the customer record decision logicto the lowest level. In embodiments, decision trees constructed by theTFMP based on a user's input may represent a series of decision points.Each decision point may be called a node and off of each node may be oneof more branches. The point at which there are no more decisions to bemade may be referred to as a leaf and used as the “end point” of abranching structure. FIG. 2 illustrates an example generic visualizationof one possible decision tree structure 200 created by the TFMP 100. Forexample, a call to a particular toll-free number may initially have anode 202 based on the area code from which the toll-free number iscalled, to segregate an east coast or west-coast technical supportstaff. Then, the next node may be a time node to segregate the time ofday between business hours where the call is routed to the technicalsupport staff, or after business hours where the call is routed to avoice-mail system. The decision tree may further branch into “leaves”204, 208 to indicate additional routing rules, such as specifying asingle termination number for a received call to be routed to, aparticular department within an organization, or some other routing treerule. The TFMP performs such routing essentially instantaneously or nearinstantaneously.

In another disclosed non-limiting embodiment, the CAD portion of theCRTB may logically lead a user to populate information including, butnot limited to, the following:

-   -   Administrative data about the toll-free customer        -   Toll-Free Number        -   Effective Date and Time        -   Control Toll Free Provider Identifier        -   End Customer Name        -   End Customer Address    -   Area of Service (AOS),    -   List of destination telephone number(s)    -   Carrier Identification Codes (CICs) for IntraLATA and InterLATA        traffic

In another disclosed non-limiting embodiment, complex customer record(CPR) decision nodes that may be supported by the TFMP include, but arenot limited to, the following:

-   -   Originating State    -   Originating Numbering Plan Area (NPA)    -   Originating LATA    -   Originating Plain Old Telephone System (POTS) Central Office        Exchange (NXX)    -   Originating POTS NPANXX    -   Originating POTS number    -   Specific date    -   Day(s) of the week    -   Time-of-day range    -   Percent load share, which may be used to automatically direct        different percentages of processed queries (calls) to different        branches below the node.

In another disclosed non-limiting embodiment, the “leaves” that may besupported by the TFMP data model at the ends of a given branch include,but are not limited to, the following:

-   -   Destination Telephone Number    -   Carrier    -   Announcement Treatment

Referring to FIG. 3, a simplified depiction of a customer recordrouting, created using the TFMP, is provided. In this simple example,starting from the left-most branched path, the three decision pathscorresponding to the decision trees branched paths may be represented asa routing from a toll-free number 300, detecting an area code 302, anexchange 304, carrier 308, and terminating telephone number 310, as inthe following example:

1. Area Code=732, NXX={699,494},Carrier=ATX-0288, Tel#=800-234-5678

-   -   2. Area Code=732, NXX=Other, Carrier=MCI-0222, Tel#=800-234-5678    -   3. Area Code=Other, NXX=<null>, Carrier=MCI-0222,        Tel#=800-234-5678.

Continuing the example of FIG. 3, using the TFMP, the CRTB toll may bebuilt in such a manner to allow a user to work though the decision treeand anticipate/prepopulate information based upon the informationalready provided in this build or also information provided in previouscustomer record entries. Once a default customer record template isbuilt, the TFMP may invoke this template when creating a customer recordfor a new number, thus reducing the time and effort for a subsequentcustomer record to be built. Invocation of the default customer recordtemplate by the TFMP may also serve to reduce human error associatedwith the manual creation of such records insofar as the template mayalready embody necessary data, thereby not requiring a user to rememberor retrieve the same.

Referring to FIG. 4, the methods and systems of the present disclosuremay provide for pre-populating a call routing template based on naturallanguage inputs including, associating a natural language element 400with a telecommunications routing code 402, the telecommunicationsrouting code associated with decision tree logic associating routing ofincoming calls to a toll-free telecommunications number 404; storing theassociation in a database 408 that is associated with a toll-freetelecommunications system; receiving a natural language input 412 from auser 410, the natural language input 412 may include the naturallanguage element 400; selecting the telecommunications routing code 414based at least in part on the stored association 404; populating thetelecommunications routing code 418 at a node of a call routing decisiontree 420 to generate a populated call routing decision tree 422; andstoring the populated call routing decision tree as a call routingtemplate 424 that may be identified and presented to a user interfacebased at least in part on the natural language input.

In embodiments, a natural language input may be a text or voice element.A text element may be a scanned text element. A voice element may beobtained by voice recognition software.

In embodiments, decision tree logic may determine the call path taken byan incoming toll-free call to a termination number, the call path takenby an incoming toll-free call based at least in part on the time of daythe incoming call is received, the call path taken by an incomingtoll-free call based at least in part on the geographic location of thedevice from which the incoming call is received, the call path taken byan incoming toll-free call within a business entities telecommunicationssystem, or some other call path outcome.

Further provided herein are methods and systems for creating a callrouting decision tree, the system comprising a user device of a userconfigured to receive a natural language input from a user; select astored call routing template, wherein the selection is based at least inpart on a stored association of the call routing template and a naturallanguage element that is included in the natural language input; presentthe stored call routing template to the user within a graphic userinterface; receive a command from the user, through the graphic userinterface, to associate the selected call routing template with atoll-free telecommunications number indicated by the user; and store theassociation between the call routing template and the toll-freetelecommunications number.

In embodiments, the command from the user may be text-based, such as atext-based item that is presented within the graphic user interface in amenu or other location. In embodiments, the command may be a voicecommand.

The following are illustrative clauses demonstrating non-limitingembodiments of the inventions described herein:

A method of pre-populating a call routing template based on naturallanguage inputs comprising:

-   -   associating a natural language element with a telecommunications        routing code, the telecommunications routing code associated        with decision tree logic associating routing of incoming calls        to a toll-free telecommunications number;    -   storing the association;    -   receiving a natural language input from a user, wherein the        natural language input includes the natural language element;    -   selecting the telecommunications routing code based at least in        part on the stored association;    -   populating the telecommunications routing code at a node of a        call routing decision tree to generate a populated call routing        decision tree;    -   storing the populated call routing decision tree as a call        routing template that may be identified and presented to a user        interface based at least in part on the natural language input.

A system for creating a call routing decision tree, the systemcomprising:

-   -   a user device of a user configured to:    -   receive a natural language input from a user; select a stored        call routing template, wherein the selection is based at least        in part    -   on a stored association of the call routing template and a        natural language element that is included in the natural        language input; present the stored call routing template to the        user within a graphic user interface;    -   receive a command from the user, through the graphic user        interface, to associate the selected call routing template with        a toll-free telecommunications number indicated by the user; and    -   store the association between the call routing template and the        toll-free telecommunications number.

In the current industry practice, updates and additions to toll-freeproviders numbers are not available through conventional platformreporting capabilities for up to 24 hours. This makes it difficult forend users to call up information about work done on the current day. Ifa toll-free number is reserved and for whatever reason the user does notrecord the actual number, there is often no way to find it, or alaborious search is required to assemble the necessary data elements forretrieval. One reason for the delay in the ability to report is thatreporting is sourced from a Report History Data Base (RHDB) that is onlypopulated with updates once a day. Additionally, most reporting from theRHDB is run in the background, thus in some cases, still furtherdelaying the response.

In another disclosed non-limiting embodiment, the TFMP provides the userthe ability to report on its number portfolio in real time or near realtime via an online customer dashboard. The online customer dashboard maydisplay simulated gauges and dials, business graphics such as piecharts, bar charts and graphs to provide overview that summarizes allpertinent data in one or two screens or views. The gauges and dials maybe based upon real time data that is stored within the TFMP.

The online customer dashboard may allow the user to see all its customerdata and drill down in the details in near real time. To do so, a datasource for the dashboard may maintain the data in real time or near realtime.

The online customer dashboard may provide the user with a view into theuser portfolio of toll-free number information. This may allow a user tosee basic number information about the toll-free numbers the user hasthe authority to view.

The online customer dashboard may initially provide a main dashboardscreen from which the user may drill down within a specific toll-freenumber to investigate more detailed information thereof. In one example,the main dashboard screen may provide a base set, or minimum list ofdata elements that are available, including, but not limited to, thefollowing:

-   -   User Information        -   Toll Free Provider        -   User Id        -   Last Login        -   Amount of numbers reserved    -   Number Information (a list of all toll free numbers associated        with this provider)        -   Toll Free Number        -   Number Status        -   Date Reserved        -   Date Last Updated        -   Customer Name

The user can then drill down into the particular toll free number byclicking on that particular number to find more detailed informationsuch as, Area of Service, Carrier(s), Call Routing, Reserve numbers, orother information associated with a toll-free number.

A user may also view the history of the number i.e. “the life of atoll-free number.” By selecting a particular toll free number, thehistory of use of the toll free number may be readily viewable. Variouscharts, timelines, and usage data may be included therein. Thisfunctionality may allow a user to view and report on the status andactivities of an entire RespOrg in real time, rather than parts of aRespOrg's activity and/or only at predefined time intervals (e.g., onceper day).

In another disclosed non-limiting embodiment, the online customerdashboard is not a view only tool, but may provide additional oralternative features to be customized by the user. That is individualusers may select their desired types of information available via theirdashboard.

Such features may include, but are not limited to, the following:

-   -   Customer information updates from the dashboard.    -   System alerts pertaining to all users    -   Historical customer usage information and populate information        to the user such as suggestions of available numbers    -   Alerts announcing the upcoming availability of numbers that the        customer has previously searched for    -   Billing alerts and notification of payments made

Overall, the online customer dashboard may provide a single startingpoint for any user working with toll free numbers. Having a singlelocation may allow a user of the system to use a single user interface(the dashboard) to view the entirety of activity that is associated witha plurality of toll-free numbers.

The following are illustrative clauses demonstrating non-limitingembodiments of the inventions described herein:

A user device for presenting data to a user in real time regardingchanges in metadata associated with a toll-free telecommunicationsnumber, the user device configured to:

-   -   receive an indication of a change in status of a toll-free        communications number, wherein the telecommunications number is        associated with a responsible organization that processes        toll-free telecommunications;    -   date a metadatum associated with the toll-free communications        number based at least in part on the change in status;    -   store the metadatum;    -   receive a status request from a user relating to the responsible        organization;    -   present the user with a graphic representation of the        telecommunications number's status

A method of toll-free telecommunications data visualization comprising:

-   -   presenting a data visualization dashboard to a mobile        application on a client device, wherein the presentation        includes a selectable listing of toll-free telecommunications        data parameters;    -   receiving a selection from the client device of the toll-free        telecommunications data parameters to analyze and at least one        type of data analysis to perform;    -   retrieving, in substantially real time, data relating to the        selected toll-free telecommunications data parameters;    -   analyzing the data according to the at least one type of data        analysis; and    -   presenting to the mobile application a summary of an analytic        result.

In another disclosed non-limiting embodiment, the TFMP may provide aclick-to-chat tool. The click-to-chat tool enables users to quicklycontact a support representative through the user interface, dashboard,or other interface. The click-to-chat tool may integrate with existingweb based access, provides an immediate channel to a supportrepresentative, and may facilitate support training.

In another disclosed non-limiting embodiment, the TFMP may provide asimplified two-factor authentication tool for maintaining identity andaccess security (e.g. dual factor authentication). This may eliminatethe need to use hard tokens and improve VPN accessibility.

In another disclosed non-limiting embodiment, the TFMP may provide apassword self-service tool that provides the ability for self-servicepasswords and unlock logon IDs. This may be automated via structuredemail processes.

In another disclosed non-limiting embodiment, the TFMP may provide areal-time status update tool that provides number counts and taskswithin the application. This may facilitate a real-time view of numbercounts and status (i.e. reserved, assigned, etc.)

In another disclosed non-limiting embodiment, the TFMP may provide anintegrated data stores & reporting tool that integrates data stores forconsolidated reporting. This may facilitate the creation of a singleoperational data store to eliminate separate software as a servicelicenses and consolidated reporting for responsible organizations.

In another disclosed non-limiting embodiment, the TFMP may provide asingle sign-on tool for Web Based Access (WBA), mechanized genericinterface (API), Website/Billing, Web-based Reporting System (WRS),Virtual Private Networks (VPNs), IP Multimedia Subsystem (IMS), or someother network type.

In another disclosed non-limiting embodiment, the TFMP may provide anenhanced configurability tool that allows administrators to configurethe limit of TFN that can be reserved in a single request, for example,more than 10. This may provide, for example, up to 5000 (would then do500 batch calls).

While only a few embodiments of the present disclosure have been shownand described, it will be obvious to those skilled in the art that manychanges and modifications may be made thereunto without departing fromthe spirit and scope of the present disclosure as described in thefollowing claims. All patent applications and patents, both foreign anddomestic, and all other publications referenced herein are incorporatedherein in their entireties to the full extent permitted by law.

The methods and systems described herein may be deployed in part or inwhole through a machine that executes computer software, program codes,and/or instructions on a processor. The processor may be part of aserver, client, network infrastructure, mobile computing platform,stationary computing platform, or other computing platform. A processormay be any kind of computational or processing device capable ofexecuting program instructions, codes, binary instructions and the like.The processor may be or include a signal processor, digital processor,embedded processor, microprocessor or any variant such as a co-processor(math co-processor, graphic co-processor, communication co-processor andthe like) and the like that may directly or indirectly facilitateexecution of program code or program instructions stored thereon. Inaddition, the processor may enable execution of multiple programs,threads, and codes. The threads may be executed simultaneously toenhance the performance of the processor and to facilitate simultaneousoperations of the application. By way of implementation, methods,program codes, program instructions and the like described herein may beimplemented in one or more thread. The thread may spawn other threadsthat may have assigned priorities associated with them; the processormay execute these threads based on priority or any other order based oninstructions provided in the program code. The processor may includememory that stores methods, codes, instructions and programs asdescribed herein and elsewhere. The processor may access a storagemedium through an interface that may store methods, codes, andinstructions as described herein and elsewhere. The storage mediumassociated with the processor for storing methods, programs, codes,program instructions or other type of instructions capable of beingexecuted by the computing or processing device may include but may notbe limited to one or more of a CD-ROM, DVD, memory, hard disk, flashdrive, RAM, ROM, cache and the like.

A processor may include one or more cores that may enhance speed andperformance of a multiprocessor. In embodiments, the process may be adual core processor, quad core processors, other chip-levelmultiprocessor and the like that combine two or more independent cores(called a die).

The methods and systems described herein may be deployed in part or inwhole through a machine that executes computer software on a server,client, firewall, gateway, hub, router, or other such computer and/ornetworking hardware. The software program may be associated with aserver that may include a file server, print server, domain server,internet server, intranet server, cloud server and other variants suchas secondary server, host server, distributed server and the like. Theserver may include one or more of memories, processors, computerreadable transitory and/or non-transitory media, storage media, ports(physical and virtual), communication devices, and interfaces capable ofaccessing other servers, clients, machines, and devices through a wiredor a wireless medium, and the like. The methods, programs or codes asdescribed herein and elsewhere may be executed by the server. Inaddition, other devices required for execution of methods as describedin this application may be considered as a part of the infrastructureassociated with the server.

The server may provide an interface to other devices including, withoutlimitation, clients, other servers, printers, database servers, printservers, file servers, communication servers, distributed servers andthe like. Additionally, this coupling and/or connection may facilitateremote execution of program across the network. The networking of someor all of these devices may facilitate parallel processing of a programor method at one or more location without deviating from the scope ofthe disclosure. In addition, all the devices attached to the serverthrough an interface may include at least one storage medium capable ofstoring methods, programs, code and/or instructions. A centralrepository may provide program instructions to be executed on differentdevices. In this implementation, the remote repository may act as astorage medium for program code, instructions, and programs.

The software program may be associated with a client that may include afile client, print client, domain client, internet client, intranetclient and other variants such as secondary client, host client,distributed client and the like. The client may include one or more ofmemories, processors, computer readable transitory and/or non-transitorymedia, storage media, ports (physical and virtual), communicationdevices, and interfaces capable of accessing other clients, servers,machines, and devices through a wired or a wireless medium, and thelike. The methods, programs or codes as described herein and elsewheremay be executed by the client. In addition, other devices required forexecution of methods as described in this application may be consideredas a part of the infrastructure associated with the client.

The client may provide an interface to other devices including, withoutlimitation, servers, other clients, printers, database servers, printservers, file servers, communication servers, distributed servers andthe like. Additionally, this coupling and/or connection may facilitateremote execution of program across the network. The networking of someor all of these devices may facilitate parallel processing of a programor method at one or more location without deviating from the scope ofthe disclosure. In addition, all the devices attached to the clientthrough an interface may include at least one storage medium capable ofstoring methods, programs, applications, code and/or instructions. Acentral repository may provide program instructions to be executed ondifferent devices. In this implementation, the remote repository may actas a storage medium for program code, instructions, and programs.

The methods and systems described herein may be deployed in part or inwhole through network infrastructures. The network infrastructure mayinclude elements such as computing devices, servers, routers, hubs,firewalls, clients, personal computers, communication devices, routingdevices and other active and passive devices, modules and/or componentsas known in the art, such that any of the methods herein or any step maybe completed instantaneously or near instantaneously. components. Thecomputing and/or non-computing device(s) associated with the networkinfrastructure may include, apart from other components, a storagemedium such as flash memory, buffer, stack, RAM, ROM and the like. Theprocesses, methods, program codes, instructions described herein andelsewhere may be executed by one or more of the network infrastructuralelements. The methods and systems described herein may be adapted foruse with any kind of private, community, or hybrid cloud computingnetwork or cloud computing environment, including those which involvefeatures of software as a service (SaaS), platform as a service (PaaS),and/or infrastructure as a service (IaaS).

The methods, program codes, and instructions described herein andelsewhere may be implemented on a cellular network having multiplecells. The cellular network may either be frequency division multipleaccess (FDMA) network or code division multiple access (CDMA) network.The cellular network may include mobile devices, cell sites, basestations, repeaters, antennas, towers, and the like.

The methods, program codes and instructions described herein andelsewhere may be implemented on or through mobile devices. The mobiledevices may include navigation devices, cell phones, mobile phones,mobile personal digital assistants, laptops, palmtops, netbooks, pagers,electronic books readers, music players and the like. These devices mayinclude, apart from other components, a storage medium such as a flashmemory, buffer, RAM, ROM and one or more computing devices. Thecomputing devices associated with mobile devices may be enabled toexecute program codes, methods, and instructions stored thereon.Alternatively, the mobile devices may be configured to executeinstructions in collaboration with other devices. The mobile devices maycommunicate with base stations interfaced with servers and configured toexecute program codes. The mobile devices may communicate on a peer topeer network, mesh network, or other communications network. The programcode may be stored on the storage medium associated with the server andexecuted by a computing device embedded within the server. The basestation may include a computing device and a storage medium. The storagedevice may store program codes and instructions executed by thecomputing devices associated with the base station.

The computer software, program codes, and/or instructions may be storedand/or accessed on machine readable transitory and/or non-transitorymedia that may include: computer components, devices, and recordingmedia that retain digital data used for computing for some interval oftime; semiconductor storage known as random access memory (RAM); massstorage typically for more permanent storage, such as optical discs,forms of magnetic storage like hard disks, tapes, drums, cards and othertypes; processor registers, cache memory, volatile memory, non-volatilememory; optical storage such as CD, DVD; removable media such as flashmemory (e.g. USB sticks or keys), floppy disks, magnetic tape, papertape, punch cards, standalone RAM disks, Zip drives, removable massstorage, off-line, and the like; other computer memory such as dynamicmemory, static memory, read/write storage, mutable storage, read only,random access, sequential access, location addressable, fileaddressable, content addressable, network attached storage, storage areanetwork, bar codes, magnetic ink, and the like.

The methods and systems described herein may transform physical and/oror intangible items from one state to another. The methods and systemsdescribed herein may also transform data representing physical and/orintangible items from one state to another.

The elements described and depicted herein, including in flow charts andblock diagrams throughout the figures, imply logical boundaries betweenthe elements. However, according to software or hardware engineeringpractices, the depicted elements and the functions thereof may beimplemented on machines through computer executable transitory and/ornon-transitory media having a processor capable of executing programinstructions stored thereon as a monolithic software structure, asstandalone software modules, or as modules that employ externalroutines, code, services, and so forth, or any combination of these, andall such implementations may be within the scope of the presentdisclosure. Examples of such machines may include, but may not belimited to, personal digital assistants, laptops, personal computers,mobile phones, other handheld computing devices, medical equipment,wired or wireless communication devices, transducers, chips,calculators, satellites, tablet PCs, electronic books, gadgets,electronic devices, devices having artificial intelligence, computingdevices, networking equipment, servers, routers and the like.Furthermore, the elements depicted in the flow chart and block diagramsor any other logical component may be implemented on a machine capableof executing program instructions. Thus, while the foregoing drawingsand descriptions set forth functional aspects of the disclosed systems,no particular arrangement of software for implementing these functionalaspects should be inferred from these descriptions unless explicitlystated or otherwise clear from the context. Similarly, it will beappreciated that the various steps identified and described above may bevaried, and that the order of steps may be adapted to particularapplications of the techniques disclosed herein. All such variations andmodifications are intended to fall within the scope of this disclosure.As such, the depiction and/or description of an order for various stepsshould not be understood to require a particular order of execution forthose steps, unless required by a particular application, or explicitlystated or otherwise clear from the context.

The methods and/or processes described above, and steps thereof, may berealized in hardware, software or any combination of hardware andsoftware suitable for a particular application. The hardware may includea dedicated computing device or specific computing device or particularaspect or component of a specific computing device. The processes may berealized in one or more microprocessors, microcontrollers, embeddedmicrocontrollers, programmable digital signal processors or otherprogrammable device, along with internal and/or external memory. Theprocesses may also, or instead, be embodied in an application specificintegrated circuit, a programmable gate array, programmable array logic,or any other device or combination of devices that may be configured toprocess electronic signals. It will further be appreciated that one ormore of the processes may be realized as a computer executable codecapable of being executed on a machine readable medium.

The computer executable code may be created using a structuredprogramming language such as C, an object oriented programming languagesuch as C++, or any other high-level or low-level programming language(including assembly languages, hardware description languages, anddatabase programming languages and technologies) that may be stored,compiled or interpreted to run on one of the above devices, as well asheterogeneous combinations of processors, processor architectures, orcombinations of different hardware and software, or any other machinecapable of executing program instructions.

Thus, in one aspect, each method described above and combinationsthereof may be embodied in computer executable code that, when executingon one or more computing devices, performs the steps thereof. In anotheraspect, the methods may be embodied in systems that perform the stepsthereof, and may be distributed across devices in a number of ways, orall of the functionality may be integrated into a dedicated, standalonedevice or other hardware. In another aspect, the means for performingthe steps associated with the processes described above may include anyof the hardware and/or software described above. All such permutationsand combinations are intended to fall within the scope of the presentdisclosure.

While the disclosure has been disclosed in connection with the preferredembodiments shown and described in detail, various modifications andimprovements thereon will become readily apparent to those skilled inthe art. Accordingly, the spirit and scope of the present disclosure isnot to be limited by the foregoing examples, but is to be understood inthe broadest sense allowable by law.

What is claimed: 1-20. (canceled)
 21. A method of populatingtelecommunications call routing based on a shared attribute with astored call routing template comprising: storing a customer recordtemplate associated with a first toll-free number as a default customerrecord template, wherein the default customer record template includes afirst call routing template containing a call routing decision treelogic and at least one stored attribute associated with the firsttoll-free number; receiving a request for customer record template data,wherein the request includes the stored attribute; selecting the defaultcustomer record template based at least in part on the stored attributeassociated with the first toll-free number; and populating at least aportion of a second call routing template for a second toll-free numberbased at least in part on call routing data within the first callrouting template included in the default customer record.
 22. The methodof claim 21, wherein the shared attribute is a customer administrativedatum.
 23. The method of claim 22, wherein the customer administrativedatum is an end customer name.
 24. The method of claim 22, wherein thecustomer administrative datum is an end customer address.
 25. The methodof claim 22, wherein the customer administrative datum is an area ofservice.
 26. The method of claim 22, wherein the customer administrativedatum is a destination telephone number.
 27. The method of claim 22,wherein the customer administrative datum is a carrier identificationcode.
 28. The method of claim 21, wherein the shared attribute is a callprocessing record datum.
 29. The method of claim 28, wherein the callprocessing record datum is an originating numbering plan area.
 30. Themethod of claim 28, wherein the call processing record datum is anoriginating central office exchange.
 31. The method of claim 28, whereinthe call processing record datum is an originating Plain Old TelephoneSystem (POTS) number.
 32. The method of claim 28, wherein the callprocessing record datum is a destination telephone number.
 33. Themethod of claim 28, wherein the call processing record datum is acarrier name.
 34. The method of claim 21, wherein the decision treelogic determines a call path taken by an incoming toll-free call to atermination number.
 35. The method of claim 21, wherein the decisiontree logic determines a call path taken by an incoming toll-free callbased at least in part on a time of day an incoming call is received.36. The method of claim 21, wherein the decision tree logic determines acall path taken by an incoming toll-free call based at least in part ona geographic location of a device from which the incoming toll-free callis received.
 37. The method of claim 21, wherein the decision tree logicdetermines a call path taken by an incoming toll-free call within atelecommunications system.
 38. A user device for presenting data to auser in real time regarding changes in metadata associated with acustomer record template, the user device configured to: receive anindication of a change in status of a default customer record templatethat is associated with a first toll-free telecommunications number,wherein the first toll-free telecommunications number is associated witha responsible organization that processes toll-free telecommunications;update a metadatum associated with the default customer record templatebased at least in part on the change in status; store the updatedmetadatum and default customer record template, wherein the storeddefault customer record template includes a change to a first callrouting template associated with the first telecommunications number;identify a second call routing template associated with a secondtoll-free telecommunications number, wherein the identification is basedat least in part on the updated metadatum; and update the second callrouting template based at least in part on the change to the callrouting template associated with the first toll-free telecommunicationsnumber.
 39. The user device of claim 38, wherein the presentationincludes presenting a status for a plurality of telecommunicationnumbers associated with the responsible organization, wherein the statuspresented is based on a real time status change occurring over atoll-free telecommunications network.
 40. The user device of claim 39,wherein the real time status change occurring over a toll-freetelecommunications network is a datum summarizing telecommunicationsnetwork congestion.